Skip to main content

Data Flow Diagrams

📊 Common for All Models​

ODIN Connector supports multiple models for connectivity and execution. The common flow across all models involves the Publisher requesting a Broker list, and the ODIN Connector returning the Broker–Publisher mapping list with the respective Partner IDs of Brokers.

Common Module

🧱 Model 1: Redirect​

User is redirected from your platform to the broker's platform to log in and execute trades.

Flow:

  1. Publisher redirects with Partner ID → ODIN Connector validates and redirects to respective broker
  2. User logs in with credentials at the broker
  3. Broker sends user data to Connector
  4. User is logged in (or created) on VAS
  5. On success, Connector calls Publisher for basket details
  6. Publisher returns basket data with Reco ID
  7. Basket is rendered; user submits → redirects back to ODIN Connector callback
  8. Connector redirects to Publisher callback endpoint → Publisher displays success message

Model 1

Model 2: 🔑🔌 Login with Broker (Smart Session)​

User can register and log in to your platform using trading credentials. At the time of transaction, the user is taken to the Broker's page for execution.

Flow:

  1. Publisher redirects with Partner ID → ODIN Connector validates and redirects
  2. Broker authenticates user and sends data with session to Connector
  3. UserSession is shuffled before callback
  4. Publisher saves session token
  5. On subsequent trade requests, session is passed → if valid, login page is bypassed
  6. Broker calls ODIN Connector for basket details → Publisher returns basket data with Race ID
  7. Basket rendered → user submits → redirected to Publisher callback

Model 2

Model 3: 🤖 Auto Trading Without Invoking Broker Pages​

Completely API-based flow where you control the user's experience of transacting from your application.

Flow:

  1. Publisher requests Broker list → Connector returns mapping with Partner IDs
  2. Publisher requests Broker Endpoint / API Key → Connector returns endpoint and API Key
  3. Publisher uses endpoint and API Key to directly call ODIN APIs

Model 3